<sqlConnection>connection-string</sqlConnection> Defines the database connection string.

<sqlCommand>stored-procedure-name</sqlCommand> Defines the SQL command to be executed.

<sqlParameter identifier="name" >parameter-name<sqlParameter> Defines the SQL parameters.

<sqlColumn identifier="name" >column-name<sqlColumn> Defines the SQL parameters.

<csvFilename>CSV-filename</csvFilename>

<csvCommand csvColumn="name-or-index" equals|contains|equalsIdentifier|containsIdentifier="name"/>

<csvColumn identifier="name" >column-name-or-index<sqlColumn>

CREATE PROCEDURE [dbo].[GetContactDetails]
	@username varchar(50),
	@email varchar(100) output,
	@mobile varchar(16) output
AS
BEGIN
	SELECT @email=Email, @mobile=Mobile
		FROM Users
	WHERE UserName=@username
END

The corresponding XML would be as below. Note how one identifier is defined for and associated with each SQL parameter, both input and output.

<mkzAttachment type="dataQuery">
	<onSubmit> 
		<!-- define an identifier for each parameter of the stored procedure -->
		<setIdentifier name="patientName" scan="X,Y,W,H" extract="MRN:" />
		<setIdentifier name="patientEmail">empty</setIdentifier>
		<setIdentifier name="patientMobile">empty</setIdentifier>
		
		<sqlConnection>Data Source=SERVER;Initial Catalog=NAME;IntegratedSecurity=True </sqlConnection>
		
		<!-- specify the procedure and  associate each identifier with a parameter -->
		<sqlCommand>GetContactDetails
			<sqlParameter identifier="patientName">username</sqlParameter>
			<sqlParameter identifier="patientEmail" direction="out">email </sqlParameter>
			<sqlParameter identifier="patientMobile" direction="out">mobile </sqlParameter>
		</sqlCommand>

	</onSubmit>
</mkzAttachment>

After the SQL procedure executes, identifiers associated with SQL ‘out’ parameters will have been set to the returned values.

CREATE PROCEDURE [dbo].[GetLetterReturnAddress]
	@UniqueID bigint
AS
BEGIN
	SELECT o.Name + ',' + o.Address AS 'Address'
	FROM Letters l
	JOIN Organisation o ON l.OrganisationID=o.OrganisationID
	WHERE l.UniqueID = @UniqueID
END

The corresponding XML would be as below. Note how one identifier is defined for and associated with each SQL parameter and each column that will be returned.

<mkzAttachment type="dataQuery">
	<onSubmit>
		<!-- define an identifier for each parameter of the stored procedure, and for each column to be returned -->
		<setIdentifier name="letterID" letterValue="id" />
		<setIdentifier name="orgAddress" >unknown</setIdentifier>
		
		<sqlConnection>Data Source=SERVER;Initial Catalog=NAME;Integrated Security=True </sqlConnection>
		
		<!-- specify the procedure and  associate each identifier with either a parameter or a column name -->
		<sqlCommand>GetLetterReturnAddress
			<sqlParameter identifier="letterID">UniqueID</sqlParameter>
			<sqlColumn identifier="orgAddress">Address</sqlColumn>
		</sqlCommand>
	</onSubmit>
</mkzAttachment>

After the SQL procedure executes, identifiers associated with columns will have been set to the column values.

The corresponding XML would be as below. Note how one identifier is defined for and associated with, the required row and each column that will be returned.

<mkzAttachment type="dataQuery">
	<onSubmit>
		<!-- define an identifier to compare with the required row, and for each column to be returned -->
		<!-- In this example we will assume that the scanned user name is "fredbloggs" -->
		<setIdentifier name="scannedUser" scan="100,50,20,10" /> 
		<setIdentifier name="email" >null</setIdentifier>
		<setIdentifier name="phone" >null</setIdentifier>

		<csvFilename>c:\myfiles\users.csv</csvFilename>

		<!-- associate each identifier with either the required row or a column name -->	
		<csvCommand csvColumn="username" equalsIdentifier="scannedUser" >
			<csvColumn identifier="email">email</csvColumn> 
			<csvColumn identifier="phone">tel</csvColumn>
		</csvCommand>
	</onSubmit>
</mkzAttachment>

When applied to the file above, the above query would result in: